Wheel detection and its application in object tracking and sensor registration

ABSTRACT

A method and system are disclosed for tracking a remote vehicle which is driving in a lateral position relative to a host vehicle. Target data from two radar sensors are provided to an object detection fusion system. Wheels on the remote vehicle are identified as clusters of radar points with essentially the same location but substantially varying Doppler range rate values. If both wheels on the near side of the remote vehicle can be identified, a fusion calculation is performed using the wheel locations measured by both radar sensors, yielding an accurate estimate of the position, orientation and velocity of the remote vehicle. The position, orientation and velocity of the remote vehicle are used to trigger warnings or evasive maneuvers in a Lateral Collision Prevention (LCP) system. Radar sensor alignment can also be calibrated with an additional fusion calculation based on the same wheel measurement data.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates generally to a lateral vehicle object detection system and, more particularly, to an object detection system which identifies the unique motion signature of wheels in radar point data to locate a remote vehicle's wheels, and uses the remote vehicle wheel locations to accurately determine the position, orientation and velocity of the remote vehicle, and simultaneously calibrate radar sensor alignment.

2. Discussion of the Related Art

Object detection systems, also known as object sensing systems, have become increasingly common in modern vehicles. Object detection systems can provide a warning to a driver about an object in the path of a vehicle. Object detection systems can also provide input to active vehicle systems—such as Adaptive Cruise Control, which controls vehicle speed to maintain appropriate longitudinal spacing to a leading vehicle, and Rear Cross Traffic Avoidance systems, which can provide both warnings and automatic braking to avoid a collision with an object behind a host vehicle when the host vehicle is backing up.

Object detection systems use one or more sensors, which may be radar, lidar, camera, or other technologies, to detect the presence of an object in or near the path of a host vehicle. Software is used to track the relative motion of objects over time, determine if the objects are moving or stationary, determine what each object is likely to be (another vehicle, a pedestrian, a tree, etc.), and determine whether each object poses a collision threat to the host vehicle.

However, even with multiple object sensing inputs, such as radar and camera, it is not always possible to accurately estimate the heading of a remote vehicle or object, especially if the remote vehicle or object is moving in a predominantly lateral or tangential direction relative to the host vehicle. Furthermore, in some situations, it is difficult to accurately correlate radar point data with camera image data. Fusion techniques are needed which provide accurate two-dimensional velocity of remote vehicles and objects, using object data from a camera and two radar sensors.

SUMMARY OF THE INVENTION

In accordance with the teachings of the present invention, a method and system are disclosed for tracking a remote vehicle which is driving in a lateral position relative to a host vehicle. Target data from two radar sensors are provided to an object detection fusion system. Wheels on the remote vehicle are identified as clusters of radar points with essentially the same location but substantially varying Doppler range rate values. If both wheels on the near side of the remote vehicle can be identified, a fusion calculation is performed using the wheel locations measured by both radar sensors, yielding an accurate estimate of the position, orientation and velocity of the remote vehicle. The position, orientation and velocity of the remote vehicle are used to trigger warnings or evasive maneuvers in a Lateral Collision Prevention (LCP) system. Radar sensor alignment can also be calibrated with an additional fusion calculation based on the same wheel measurement data.

Additional features of the present invention will become apparent from the following description and appended claims, taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a host vehicle including multiple object detection sensors;

FIG. 2 is an illustration of the host vehicle of FIG. 1, along with a remote vehicle, showing how the velocity vector of the remote vehicle affects its incursion into a warning zone or braking envelope of the host vehicle;

FIG. 3 is an illustration of the host vehicle and the remote vehicle of FIG. 2, further illustrating the difficulty in obtaining an accurate 2-D velocity of the remote vehicle;

FIG. 4 is another illustration of the host vehicle and the remote vehicle, showing salient vision points and radar points which are used by an object sensing fusion system on the host vehicle to determine velocity of the remote vehicle;

FIG. 5 is a flowchart diagram of a method for calculating a velocity of a remote object relative to a host vehicle using a fusion of salient vision points with radar points;

FIG. 6 is a flowchart diagram of a method for tracking salient vision points on a remote object from camera images;

FIG. 7 is a flowchart diagram of a method for associating salient vision points with radar points in an object tracking system;

FIG. 8 is a schematic diagram of a host vehicle including multiple object detection sensors in a side view configuration;

FIG. 9 is an illustration of the host vehicle as depicted in FIG. 8, along with a remote vehicle, where the remote vehicle is driving generally alongside the host vehicle;

FIG. 10 is a side-view illustration of a tire and wheel rolling on the ground, showing the basic motion properties which can be used to identify wheels in radar sensor data;

FIGS. 11 and 12 are top-view diagrams of the host vehicle and the remote vehicle of FIG. 9, illustrating the principles and geometric relationships on which wheel detection, remote vehicle tracking and radar sensor calibration are based;

FIG. 13 is a flowchart diagram of a method for detecting a remote vehicle's wheels based on the measurement technique described and shown on FIGS. 11 and 12; and

FIG. 14 is a flowchart diagram of a method for simultaneously tracking the remote vehicle and calibrating the alignment angles of the radar sensors using remote vehicle wheel detection.

DETAILED DESCRIPTION OF THE EMBODIMENTS

The following discussion of the embodiments of the invention directed to a method and apparatus for tracking a remote vehicle by detecting its wheels in radar sensor point data is merely exemplary in nature, and is in no way intended to limit the invention or its applications or uses.

Many modern vehicles include an object sensing system for detecting objects in the path of the vehicle. The object sensing system can provide a warning to a driver, or even trigger other systems to take action to avoid a vehicle collision. Some vehicles also include an object sensing fusion system, which numerically “fuses” the data from two or more object detection sensors and then bases its object detection logic on the fused object data. One such fusion system is described in U.S. Pat. No. 7,460,951, titled “System and method of target tracking using sensor fusion”, which is assigned to the assignee of the present application, and which is hereby incorporated by reference in its entirety.

FIG. 1 is a schematic diagram of a host vehicle 10 including multiple object detection sensors. The host vehicle 10 includes an object sensing fusion system 12, which receives data from a camera 20 and a pair of radar sensors 32 and 34. The fusion system 12 comprises a device including a microprocessor and a memory module, said device being configured with software to perform object sensing fusion—as described in detail below. Other applications, besides object sensing fusion, may also run on the same microprocessor as the fusion system 12.

The camera 20 provides images to the fusion system 12 (or to a dedicated vision system, not separately shown), where the images are processed to detect, identify and track remote objects. Similarly, the radar sensors 32/34 provide their radar return data to the fusion system 12 (or to a dedicated radar tracking system, not separately shown), where the radar points are processed to detect, identify and track remote objects. The camera 20 and the radar sensors 32/34 typically communicate with and provide their data to the fusion system 12 by a wired connection over a vehicle bus, but this communication could be wireless.

The camera 20 has a field of view 22. The radar sensors 32/34 have coverage areas 36 and 38, respectively. In the FIG. 1 illustration, the camera 20 and the radar sensors 32/34 are oriented in a rearward direction, and the following discussion is directed to a rear cross traffic detection application. However, the techniques could also be applied to forward-view or side-view orientations and applications. It is to be noted that only remote vehicles or objects which exist in locations where the camera field of view 22 overlaps with the radar coverage areas 36 or 38 can be used for object fusion. This overlapping coverage area, where both the camera 20 and one of the radar sensors 32/34 can detect a target, is shown by oval 40 in FIG. 1. The sizes and shapes of the field of view 22, the radar coverage areas 36/38 and the overlapping coverage oval 40 are all shown conceptually in FIG. 1, as would be understood by one skilled in the art.

However, even with two or more object sensors, it may be difficult for a traditional object sensing fusion system to accurately determine the two-dimensional (2-D) velocity of a remote vehicle or object, particularly if the remote vehicle or object is moving in a predominantly lateral (or tangential) direction relative to a host vehicle. The nature of this problem is illustrated in FIGS. 2 and 3.

FIG. 2 is an illustration of the host vehicle 10 of FIG. 1, along with a remote vehicle 50. FIG. 2 depicts a typical parking lot scenario, where the host vehicle 10 is backing up as indicated by velocity arrow 18, and the remote vehicle 50 is driving towards a position behind the host vehicle 10 that may cause a conflict. In rear cross traffic avoidance (ROTA) systems, the host vehicle 10 may have a brake envelope 14 defined about it, where the brakes of the host vehicle 10 may be automatically applied if the host vehicle 10 is moving and an object enters the brake envelope 14. The host vehicle 10 may also have a warning zone 16 defined, where an audible and/or visual warning is issued to the driver of the host vehicle 10 if an object enters the warning zone 16.

The velocity of the remote vehicle 50 is an important parameter to be known by the ROTA system. This is because the ROTA system needs the velocity of the remote vehicle 50 in order to determine an estimated “time to enter” the warning zone 16 and/or the brake envelope 14. In addition, the position of the warning zone 16 may be based upon the velocity of the remote vehicle 50. It can be clearly seen in FIG. 2 that the warning and actions taken by the ROTA system would be very different if the remote vehicle 50 has a first velocity 52 than if the remote vehicle 50 has a second velocity 54. Thus, it is apparent that an accurate 2-D velocity of the remote vehicle 50 is needed.

FIG. 3 is an illustration of the host vehicle 10 and the remote vehicle 50, further illustrating the difficulty in obtaining an accurate 2-D velocity of the remote vehicle 50. In FIG. 3, the remote vehicle 50 has an actual velocity v designated by arrow 60. The actual velocity v can be considered to be comprised of two orthogonal components—a radial velocity designated by arrow 62 and a tangential velocity designated by arrow 64. The radar sensors 32/34 typically include Doppler capability, where radar returns not only indicate the location of an object point but also the radial velocity v of the point. Thus, the radial velocity v of points on the remote vehicle 50 can be accurately determined from radar sensor data. However, it is difficult to estimate the tangential velocity through conventional target tracking. This is because the remote vehicle 50 is a large object which cannot be considered a point target. Because the radar sensors 32/34 will sense many radar return points from the remote vehicle 50, and each scan may return different points, azimuth angle measurement is uncertain. This in turn leads to tangential velocity uncertainty.

Image-based object detection systems are better suited to estimating tangential velocity of a target, by calculating movement of the target in the image plane over a period of time. However, in the case of a vehicle such as the remote vehicle 50, traditional techniques for doing this are often unsatisfactory; this is because the apparent lateral motion of the target in the image plane can be affected by radial velocity (which causes the target to appear larger or smaller in subsequent frames), or by frame-to-frame differences in cropping of the vehicle outline.

From the above discussion, is it apparent that an improved fusion/tracking technique is needed which can accurately estimate the 2-D velocity of the remote vehicle 50. Such a technique can be realized by fusing camera image data (i.e., vision data) with radar return data. In the fusion technique discussed below, the radar return data provides accurate radial velocity, as described above. At the same time, salient points (i.e., prominent or conspicuous points) in the camera image data can provide accurate lateral or tangential velocity. That is, instead of merely treating the remote vehicle 50 as a single object for tracking purposes, multiple features from the remote vehicle 50 are individually tracked in the images. In order to improve the quality and reliability of the results, salient vision points can be associated with radar points using position proximity in the image plane, and using previously estimated object velocity as cueing. Salient vision points with different lateral speed than expected based on current and previous measurements can be removed from the calculation.

In the technique disclosed here, salient vision points on the remote vehicle 50 may include Harris corners (locations of locally maximal intensity variation, such as where a vehicle A-pillar meets a hoodline/doorline), wheels, head lights, tail lights, door handles, external mirrors, and any Maximally Stable Extremal Region (MSER) or other prominent features. Scale Invariant Feature Transform (SIFT) techniques may also be used to detect and describe salient vision points in the images. Features from Accelerated Segment Test (FAST), a corner detection method, could be used to extract salient points and later used for tracking and velocity estimation. Binary Robust Independent Elementary Features (BRIEF) and Oriented FAST and Rotated BRIEF (ORB) can be used for detection of feature points for objects.

FIG. 4 is another illustration of the host vehicle 10 and the remote vehicle 50, showing salient vision points and radar points which are used in the ensuing discussion. In FIG. 4, the remote vehicle 50 again has a velocity v represented by the arrow 60. The radar sensors 32/34 onboard the host vehicle 10 detect a number of radar points, shown as circles 80, and the camera 20 detects a number of salient vision points, shown as squares 90. As indicated by the small arrows, the radar points will include Doppler radial velocity ({dot over (r)}) data, and the salient vision points will have an apparent motion flow across the image plane which correlates to lateral velocity. A technique for associating the salient vision points and radar points and fusing the data to produce an accurate estimate of the velocity v is discussed in detail below.

FIG. 5 is a flowchart diagram 100 of an overall method for calculating a velocity of a remote object relative to a host vehicle using a fusion of salient vision points with radar points. At box 102, data is provided by the camera 20 and the radar sensors 32/34. For the purposes of this discussion, the data from the box 102 is provided to, and all subsequent calculations are performed on, the fusion system 12—which includes a microprocessor and a memory module as discussed previously. In actual implementation on a vehicle, the calculations could be performed on any suitable controller or processor, or could be distributed across more than one processor.

At box 104, radar data is used for cueing or triggering the subsequent calculations. That is, if an object is detected by the radar sensors 32/34 in a region of interest (ROI) behind the host vehicle 10, this cues the process to continue with the velocity fusion calculations. At box 106, salient vision points are identified and tracked using the camera image data. FIG. 6 is a flowchart diagram 140 of a method for tracking salient points on a remote object from camera images. The method of FIG. 6 is implemented at the box 106 of FIG. 5. At box 142, salient vision points in the region of interest are detected from an image frame. As discussed above, the salient vision points are prominent features of the object (in this case, the remote vehicle 50)—such as pillar ends, wheels, head lights, etc.

At box 144, a correspondence between two temporally adjacent image frames is built. That is, salient vision points which can be identified in a first image frame and the next image frame are noted. Of course, the salient points will have moved in the image plane from one image to the next, and they will not appear identical (pixel for pixel) for many reasons—including change of perspective, change of lighting/reflection, etc. At box 146, salient vision points which are stable (that is, moving in a predictable manner) across image frames are detected. A method for detecting spatio-temporally stable salient vision points using a minimal cost flow network was described in U.S. patent application Ser. No. 13/535,538 (Attorney Docket No. P019555-RD-SDJ), Titled “WIDE BASELINE BINOCULAR OBJECT MATCHING METHOD USING MINIMAL COST FLOW NETWORK”, filed 28 Jun. 2012, assigned to the assignee of the present invention, and hereby incorporated by reference.

At box 148, the motion flow for each stable salient point is established. The motion flow is not an actual velocity; rather, it is a movement of a salient point in the image plane of the camera 20 from one frame to the next. Knowing the elapsed time between image frames, the motion flow can thus be identified in pixels per second, for example. Per the following discussion, the motion flow of the salient points can be transformed and used in a fusion calculation which does yield velocity of the detected object.

Returning to FIG. 5, the salient point motion flow data from the flowchart diagram 140 is now available at the box 106. At box 108, the salient vision points from the box 106 are associated with radar points. FIG. 7 is a flowchart diagram 180 of a method for associating salient vision points with radar points in an object tracking system. The method of FIG. 7 is implemented at the box 108 of FIG. 5. At box 182, each radar point p_(i) is projected to the image plane. That is, ũ_(i)=H(p_(i)), where H is the homography transformation from the x-y frame to the image plane, and ũ_(i) is the projected radar point, assuming these radar points lie on the ground plane. At box 184, a predicted object velocity v (from previous time step) is projected to the image plane as motion flow F. That is, F=∂H|_(p)v if the object is at a location p in the x-y frame, where ∂H|_(p) is the Jacobian matrix of the transformation H computed at locate p. At box 186, salient vision points with a motion flow different than expected are screened out, or removed from subsequent calculations. That is, a j-th vision point is removed from the calculations if ∥f_(j)−F∥>T, where f_(j) is the estimated motion flow of the j-th vision point, and T is a threshold motion flow difference, where T could be either a fixed value or a percentage of F.

At box 188, each of the remaining salient vision points u_(j) (those not removed at the box 186) is assigned to its nearest radar point (transformed to the image plane) ũ_(i), where the distance (for determination of nearest) is measured in image pixel columns. As a result of this assignment, q_(j)=p_(i) in the x-y frame, where q_(j) is the projection of the vision point u_(j) from the image plane to the x-y frame using the homography transformation H, and p_(i) is the nearest radar point.

Returning to FIG. 5, the salient vision points (numbering M) have now been associated with the radar points (numbering N) at the box 108. At box 110—with the salient vision points and their motion flow (u_(j),f_(j)), and the radar points and their radial velocity (p_(i),{dot over (r)}_(i)) identified and associated as described above—the velocity v of the remote vehicle 50 (the object being measured by the salient vision points and the radar points) can be determined by minimizing the following:

$\begin{matrix} \left. \left. {{\sum\limits_{i = 1}^{N}\; \left( {\frac{p_{i} \cdot v}{\left. ||p_{i} \right.||} - {\overset{.}{r}}_{i}} \right)^{2}} + \sum\limits_{j = 1}^{M}}\;||{\partial H} \right. \middle| {}_{q_{j}}\left. {v - f_{j}} \right.||^{2} \right. & (1) \end{matrix}$

Where all of the variables in Equation (1) have been defined and discussed above.

At box 112, the velocity v of the remote vehicle 50 is used in a driver-assistance application such as a rear cross traffic avoidance (ROTA) system. As discussed previously, the velocity v of the remote vehicle 50 may be used to calculate a “time to enter” the warning zone 16 and/or the brake envelope 14, and the position of the warning zone 16 may be based upon the velocity v of the remote vehicle 50. The process of the flowchart diagram 100 continues, and the velocity of the remote vehicle 50 is continually updated using the fusion calculation of Equation (1), as long as an object is detected in the region of interest behind the host vehicle 10.

The velocity calculation employing fusion of salient vision points and radar points—described above—provides more accurate estimation of remote vehicle velocity than traditional object sensing methods. The accurate remote vehicle velocity can be advantageously used in a rear cross traffic avoidance (ROTA) system. This same fusion technique can also be used to track other types of objects—such as bicycles and shopping carts—and to track objects in front-view or side-view applications, wherever a camera field of view overlaps a radar coverage area. All of these capabilities are possible without the necessity for tedious training of object classifiers.

While the technique described above is very effective for detection and tracking of any general object in proximity to a host vehicle, particularly in a rear cross traffic avoidance application, other techniques can be employed for tracking remote vehicles specifically. One such technique takes advantage of the unique motion signature of the wheels on a remote vehicle, and provides enhanced calculation of the remote vehicle's position, velocity and heading.

FIG. 8 is a schematic diagram of a host vehicle 300 including multiple object detection sensors in a side view configuration. The host vehicle 300 includes an object sensing fusion system 302, which receives data from a camera 304 and a pair of radar sensors 306 and 308. The fusion system 302 comprises a device including a microprocessor and a memory module, said device being configured with software to perform object sensing fusion—as described in detail below. Other applications, besides object sensing fusion, may also run on the same microprocessor as the fusion system 302.

The camera 304 and the radar sensors 306/308 have overlapping coverage areas, and provide their data to the fusion system 302, in a manner similar to that discussed previously with respect to the host vehicle 10 of FIG. 1. As was the case in FIG. 1, the sizes and shapes of a camera field of view 314, radar coverage areas 316/318 and an overlapping coverage oval 320 (within which a remote vehicle can be detected by the camera 304 and at least one of the radar sensors 306/308) are all shown conceptually in FIG. 8, as would be understood by one skilled in the art.

As discussed previously, even with two or more object sensors, it may be difficult for a traditional object sensing fusion system to accurately determine the two-dimensional (2-D) velocity of a remote vehicle, particularly if the remote vehicle is moving in a predominantly lateral (or tangential) direction relative to the host vehicle 300. The nature of this problem, as manifested in a side view or lateral collision prevention situation, is illustrated in FIG. 9.

FIG. 9 is an illustration of the host vehicle 300 as depicted in FIG. 8, along with a remote vehicle 400. FIG. 9 illustrates a typical multi-lane roadway driving scenario, where the host vehicle 300 is driving as indicated by velocity arrow 330, and the remote vehicle 400 is driving generally alongside the host vehicle 300 but potentially drifting toward the host vehicle 300 in a direction that may cause a conflict. In lateral collision prevention (LCP) systems, the host vehicle 300 may issue a driver warning if the remote vehicle 400 enters a warning zone, or take evasive action (braking and/or steering) if the remote vehicle 400 is determined to pose an imminent collision hazard.

The velocity of the remote vehicle 400 is an important parameter to be known by the LCP system. It can be clearly seen in FIG. 9 that the warning and/or actions taken by the LCP system would be very different if the remote vehicle 400 has a first velocity 402 than if the remote vehicle 400 has a second velocity 404. Thus, it is apparent that an accurate 2-D velocity of the remote vehicle 400 is needed. In the case of a laterally positioned remote vehicle, it is possible to distinctly identify the remote vehicle's wheels, and use the remote vehicle wheel measurements to determine the 2-D remote vehicle velocity, and to simultaneously calibrate the radar sensor aiming angles.

FIG. 10 is a side-view illustration of a tire and wheel rolling on the ground, showing the basic motion properties which can be used to identify wheels in radar sensor data. In FIG. 10, a tire 260 with a wheel 270 are rolling on the ground. The wheel 270 has a radius r 272, and the tire 260 has a thickness H 262. An outer radius of the tire, R, is defined as r+H. An analysis of three points on the wheel 270—a wheel bottom point 274, a wheel center point 276, and a wheel top point 278—illustrates how the wheel can be distinctly identified in radar return data. For visualization relative to FIG. 9, consider the tire 260 and the wheel 270 to be on the right-hand side of the remote vehicle 400.

The wheel center point 276 is, of course, moving at the same velocity v (denoted by arrow 286) as the remote vehicle 400. The wheel top point 278, due to the wheel rotation, is moving at a velocity:

$\begin{matrix} {v_{278} = {\left( {1 + \frac{R - H}{R}} \right)v}} & (2) \end{matrix}$

Or, in other words, the wheel top point 278 is moving at a velocity (denoted by arrow 288) that is almost twice the remote vehicle velocity v.

Similarly, the wheel bottom point 274, due to the wheel rotation, is moving at a velocity:

$\begin{matrix} {v_{274} = {\left( {1 - \frac{R - H}{R}} \right)v}} & (3) \end{matrix}$

Or, in other words, the wheel bottom point 274 is moving at an absolute velocity (denoted by arrow 284) that is slightly greater than zero.

Wheels are good radar reflectors, so many radar points are likely to be returned from the wheel 270. Assuming that the wheel 270 is not perfectly perpendicular to the sight line of the radar sensors 306/308, the different velocities of the points on the wheel—as illustrated by the points 274/276/278—will result in different Doppler range-rate measurements by the radar sensors 306/308. Thus, if the sensors 306/308 detect multiple radar points at essentially the same location, with dramatically different range-rate values, these clusters of points can be considered to be a wheel on the remote vehicle 400.

In order to use remote vehicle wheel locations to track the remote vehicle 400 and calibrate the radar sensor aiming angles, the locations of the wheels on the remote vehicle 400 must first be identified in the radar data. FIGS. 11 and 12 are top-view diagrams of the host vehicle 300 and the remote vehicle 400, illustrating the principles and geometric relationships on which the following discussion and calculations—describing wheel detection, remote vehicle tracking and radar sensor calibration—are based.

The host vehicle 300 has a centroid 332 which serves as the origin of an X-Y coordinate frame as shown. The radar sensors 306 and 308 are each located at a position p_(l) in the host vehicle frame, where l=0,1. Thus, the radar sensor 306 may be designated as R₀ located at a position p₀ (designated by vector 342), and the radar sensor 308 may be designated as R₁ located at a position p₁ (designated by vector 352). Similarly, the radar sensor 306 (R₀) has a sight line 344 which is situated at an angle φ₀ (angular measure 346) from the straight-ahead (X) direction of the host vehicle 300, and the radar sensor 308 (R₁) has a sight line 354 which is situated at an angle φ₁ (angular measure 356) from the straight-ahead (X) direction of the host vehicle 300.

The remote vehicle 400 has a centroid 406, and is moving with a velocity v along the vector 402, which is at an angle θ (angular measure 408) from the straight-ahead (X) direction of the host vehicle 300. The remote vehicle 400 has right-side wheels 410 and 412. For the purposes of this discussion, the remote vehicle 400 is a car or truck with four wheels (two on each side); however, the wheel detection method is equally applicable to remote vehicles with two wheels (motorcycles) and remote vehicles with more than four wheels (trucks and buses). Each of the wheels on the remote vehicle 400 are located at a position q_(k) (designated by vector 414) in the remote vehicle frame, where k=0, . . . , 3.

As discussed above, the first task is to detect the wheels 410 and 412 on the remote vehicle 400, which is done by identifying clusters of radar points at the same location with a range of Doppler (range rate) measurements. For the wheel 270 of FIG. 10, the relative velocity {right arrow over (v)} of the wheel top point 278 with respect to the host vehicle 300, a component of which is equal to the range rate of the point 278 which would be detected by the radar sensors 306/308, can be defined as:

$\begin{matrix} {\overset{\rightarrow}{v} = \begin{bmatrix} {{\left( {1 + \frac{r}{R}} \right)v\mspace{14mu} {\cos (\theta)}} - v_{H}} \\ {\left( {1 + \frac{r}{R}} \right)v\mspace{14mu} \sin \mspace{14mu} (\theta)} \end{bmatrix}} & (4) \end{matrix}$

Where r is the wheel radius, R is the tire radius, v is the velocity of the remote vehicle 400, θ is the heading angle of the remote vehicle 400 and v_(H) is the velocity of the host vehicle 300.

Similarly, the wheel bottom point 274 is moving at a relative velocity with respect to the host vehicle 300 which can be obtained by using a variation of Equation (4) where the (1+r/R) factor is replaced by (1−r/R). In most circumstances, the wheel bottom point 274 will be moving away from the host vehicle 300.

For the radar sensor 306 (R₀) measuring one of the wheels on the remote vehicle 400, as shown in FIGS. 11 and 12, a radial ray unit vector {right arrow over (v)} can be defined as:

{right arrow over (n)}=[cos(φ+φ₀)sin(φ+φ₀)]^(T)  (5)

Where φ, as shown in FIG. 12, is the azimuth measurement angle of the remote vehicle wheel relative to the sight line 344 of the radar sensor (denoted by angular measure 360, and shown as −φ because it is measured clockwise from the sight line 344, where φ₀ is measured counter-clockwise).

Knowing the relative velocity {right arrow over (v)} of a point on the remote vehicle's wheel (from Equation 4) and the radial ray unit vector {right arrow over (n)} from the radar sensor to the wheel (from Equation 5), the expected Doppler measurement D of the point on the remote vehicle's wheel can be determined as:

D={right arrow over (v)}·{right arrow over (n)}  (6)

FIG. 13 is a flowchart diagram 500 of a method for detecting a remote vehicle's wheels based on the measurement technique discussed above. At box 502, sensor points are acquired for the radar sensors 306 and 308. Each sensor point i has range, Doppler and azimuth angle. That is, each sensor point includes (r_(i), D_(i), α_(i)) for i=1, . . . , N. At box 504, radar points are clustered into groups based on positional proximity (range r, and azimuth angle α). One technique for clustering radar points into groups is to assign points i and j to the same cluster if and only if:

$\begin{matrix} {{\frac{\left| {r_{i} - r_{j}} \right|}{\sigma_{r}} - \frac{\left| {\alpha_{i} - \alpha_{j}} \right|}{\sigma_{\alpha}}} \leq 1} & (7) \end{matrix}$

Where σ_(R) and σ_(α) are tunable calibration values, and the range r and angle α were described above.

At box 506, the Doppler value of all of the radar points in each of the clusters identified in Equation (7) is evaluated. If a cluster of points has Doppler values in a range as described by Equations (4)-(6) (including some points moving toward the host vehicle 300 and some points moving away from the host vehicle 300), then that cluster is identified as a wheel on the remote vehicle 400. At box 508, a wheelbase W of the remote vehicle 400 is calculated if two wheels are detected on the remote vehicle 400, most likely the two wheels on the side nearest the host vehicle 300. The wheelbase W is calculated as the distance between the centers of the two detected wheels. The centers of the wheels may be identified as the radar points nearest the geometric center of the points included in the wheel cluster. Knowing the locations of the wheel center points from the range r and the azimuth angle α, calculating a distance between the two points is straightforward. At box 510, the orientation angle θ of the remote vehicle 400 (angular measure 408) is calculated if two wheels are detected on the remote vehicle 400. Calculation of the orientation angle θ is also straightforward, given the locations of the two wheel center points.

FIG. 14 is a flowchart diagram 540 of a method for simultaneously tracking the remote vehicle 400 and calibrating the alignment angles of the radar sensors 306/308 using remote vehicle wheel detection. The method steps of the flowchart diagram 540 may be performed by the object sensing fusion system 302 on the host vehicle 300. At box 542, radar point data is provided by the radar sensors 306/308. For the purposes of this discussion, the data from the box 542 is provided to, and all subsequent calculations are performed on, the object sensing fusion system 302—which includes a microprocessor and a memory module as discussed previously. At box 544, wheels are identified on the remote vehicle 400 in the radar point data from the sensors 306/308. If two wheels are identified, the orientation angle θ is also calculated at the box 544. Details of the steps involved in identifying the wheels of the remote vehicle 400 and calculating the orientation angle θ were provided in FIG. 13, discussed above.

At box 546, the position, orientation and velocity of the remote vehicle 400 are tracked using the wheels detected by the radar sensors 306 and 308. The state of the remote vehicle 400 is modeled as s=(x,y,v_(x),v_(y)), representing the center position r=(x,y)^(T), and ground velocity v=(v_(x), v_(y))^(T), of the remote vehicle 400. The heading or orientation angle θ of the remote vehicle 400 is related to the x and y velocities by 0=tan⁻¹(v_(y), v_(x)).

As described above in the discussion of FIGS. 11 and 12, the wheels on the remote vehicle 400 can be identified by a number k=0, . . . , 3, where each wheel is at a position q_(k) in the remote vehicle reference frame. As also described above, the radar sensors 306/308 on the host vehicle 300 can be identified by a number l=0,1, where each sensor is at a position p_(l) in the host vehicle reference frame and has a sight line angle φ_(l) from the straight-ahead (X) direction of the host vehicle 300.

Given the above, a general notation can be defined where the position of the k-th wheel measured by the l-th radar sensor is known as m_(lk).

Next, a rotational matrix Rot is defined, where Rot is used to rotate point coordinates as necessary based on the angles θ and φ. The matrix Rot is defined as:

$\begin{matrix} {{{Rot}(\phi)} = \begin{bmatrix} {\cos \mspace{14mu} \phi} & {{- \sin}\mspace{14mu} \phi} \\ {\sin \mspace{14mu} \phi} & {\cos \mspace{14mu} \phi} \end{bmatrix}} & (8) \end{matrix}$

The measurement equation for the k-th wheel measured by the l-th radar sensor (for k=0, . . . , 3 and l=0,1) based on the state s of the remote vehicle 400 is then defined as:

h _(lk)(S)≡Rot(−φ₁)(r+Rot(θ)q _(k) −p _(l))=m _(lk)  (9)

Where h_(lk) is a function of the remote vehicle state s, and the other variables were are described in the discussion above. Equation (9) can be recursively solved to optimally estimate the state S based on each new wheel position measurement m_(lk). In one non-limiting embodiment, Equation (9) is programmed in a Kalman Filter routine to solve for the state s.

By continuously solving Equation (9) using all available wheel measurements, the state of the remote vehicle 400 (x, y, v_(x), v_(y),θ) can be tracked by the host vehicle 300 at the box 546 as long as the remote vehicle 400 remains within the region of interest of the host vehicle 300.

At box 548, the alignment angles of the radar sensors 306/308 are calibrated based on the identified locations of the wheels on the remote vehicle 400. As shown in FIGS. 11 and 12, the wheel 410 on the remote vehicle 400 may be detected by both the radar sensor 306 and the radar sensor 308, thus providing redundant measurement data. The same may also be true of the wheel 412. This redundant measurement data can be advantageously used for sensor alignment calibration.

Given the known positions of the radar sensors 306 and 308 (p₀ and p₁, respectively), and their respective sight line angles (φ₀ and φ₁), Equation (9) should yield the same location q for the wheel 410 whether measured by the radar sensor 306 or the radar sensor 308. In reality, however, the redundant measurements of the wheel 410 may not agree, and any difference may be attributed to sensor misalignment. If it is assumed, for example, that the alignment angle φ₀ of the sensor 306 is accurate, then the alignment angle φ₁ of the sensor 308 can be calibrated based on the measurement data to more closely match the position r and orientation θ of the remote vehicle 400 and the location q of the wheel 410.

Extracting the second factor from Equation (9) above, a computed expression β_(t) can be defined as:

β_(t)=(r _(t)+Rot(θ_(t))q _(k) −p ₁)  (10)

Where t is a time sequence identifier, t=1, . . . , N, and the N latest values of the computed expression β_(t) and the radar measurement m_(t) are stored in a buffer.

A rotational alignment matrix R can be defined as R≡Rot(−φ₁), and can be solved by minimizing the following least-squares function:

$\begin{matrix} {\sum\limits_{t = 1}^{N}\; \left. ||{{R\; \beta_{t}} - m_{t}} \right.||^{2}} & (11) \end{matrix}$

The following technique can be used to solve Equation (11). Let matrices P=[β₁, . . . β_(N)], and M=[m₁, . . . ,m_(N)]. Matrices U, V and S are obtained by singular value decomposition of PM^(T). That is, USV^(T)=svd(PM^(T)). The solution of the least-squares Equation (11) is R=UCV^(T), where

$\begin{matrix} {C = \begin{bmatrix} 1 & 0 \\ 0 & {\det \mspace{14mu} \left( {UV}^{T} \right)} \end{bmatrix}} & (12) \end{matrix}$

And det is the determinant operator.

With the matrix R solved for above, the estimated alignment angle for the radar sensor 308 is φ₁=tan⁻¹(R₁₂,R₁₁). The alignment angle for the radar sensors 306 or 308 can be continuously calibrated at the box 548 of FIG. 14. The alignment angle can be used to adjust future measurement readings from the radar sensors 306 or 308. The tracking of the remote vehicle 400 and the simultaneous calibration of radar sensor alignment is made possible by the redundant and repeated measurement of wheels on the remote vehicle 400 by the radar sensors 306/308 on the host vehicle 300, and the fusion calculations discussed above.

The object sensing fusion system 302 may also incorporate vision data from the camera 304 in the fusion calculations discussed above, to further refine the tracking of the remote vehicle 400 and the simultaneous calibration of radar sensor alignment. This can be done by identifying wheels as salient points in the vision data and fusing the salient vision points with corresponding radar points, as discussed above with respect to the rear cross traffic avoidance (ROTA) application.

The remote vehicle tracking calculation employing radar wheel detection—described above—provides more accurate estimation of remote vehicle position, orientation and velocity than traditional object sensing methods. The accurate remote tracking can be advantageously used in a lateral collision prevention (LCP) system, where accurate knowledge of the remote vehicle's 2-D velocity is critical. Using this same fusion technique to virtually calibrate radar sensor alignment provides additional benefits to both the vehicle manufacturer and the vehicle owner/driver.

The foregoing discussion discloses and describes merely exemplary embodiments of the present invention. One skilled in the art will readily recognize from such discussion and from the accompanying drawings and claims that various changes, modifications and variations can be made therein without departing from the spirit and scope of the invention as defined in the following claims. 

What is claimed is:
 1. A method for tracking a remote vehicle which is moving in a region of interest in proximity to a host vehicle, said method comprising: providing data from two radar sensors onboard the host vehicle, where the radar sensors have coverage areas which overlap such that at least part of the remote vehicle is sensed by both of the radar sensors when the remote vehicle is in the region of interest, and where the data from the radar sensors includes radar points identifying position and Doppler range rate of points on the remote vehicle; identifying two or more wheels on the remote vehicle from the radar points; providing wheel location measurements for the two or more wheels from the two radar sensors, where the wheel location measurements identify a range and an azimuth angle of a center of each of the wheels relative to each of the radar sensors; computing, using a microprocessor, a position, orientation and velocity of the remote vehicle relative to the host vehicle, using a fusion calculation including the wheel location measurements; and computing an alignment calibration angle for one of the radar sensors using a fusion calculation including the wheel location measurements.
 2. The method of claim 1 wherein identifying two or more wheels on the remote vehicle includes clustering the radar points into groups based on positional proximity, and identifying as a wheel any of the groups which include widely varying Doppler range rate measurements.
 3. The method of claim 2 wherein clustering the radar points into groups based on positional proximity includes computing a normalized function using a difference in range values and a difference in azimuth angle values for two points, and only including the two points in a group if the normalized function has a value that does not exceed one.
 4. The method of claim 2 wherein identifying as a wheel any of the groups which include widely varying Doppler range rate measurements includes computing expected relative radial velocities of a wheel top point and a wheel bottom point on the remote vehicle with respect to the host vehicle, and identifying as a wheel any of the groups which include Doppler range rate measurements substantially matching the expected relative radial velocities of the wheel top point and the wheel bottom point.
 5. The method of claim 1 wherein computing a position, orientation and velocity of the remote vehicle relative to the host vehicle includes computing the orientation of the remote vehicle based on the wheel location measurements for two wheels on a side of the remote vehicle nearest the host vehicle.
 6. The method of claim 1 wherein computing a position, orientation and velocity of the remote vehicle relative to the host vehicle includes using an algorithm which recursively predicts a state of the remote vehicle which corresponds with the wheel measurement locations, where the state of the remote vehicle includes a two-dimensional position and a two-dimensional velocity.
 7. The method of claim 6 wherein the algorithm is a Kalman Filter algorithm.
 8. The method of claim 1 further comprising using the position, orientation and velocity of the remote vehicle in a lateral collision prevention (LCP) system, where the region of interest is located to one side of the host vehicle, and the LCP system issues a warning if the remote vehicle enters a warning zone and applies host vehicle brakes and/or steering if the remote vehicle enters a collision-imminent envelope.
 9. The method of claim 1 further comprising providing images from a camera onboard the host vehicle, where the images cover a field of view which overlaps the coverage areas of the radar sensors such that the remote vehicle is sensed by the camera and at least one of the radar sensors, and performing a fusion calculation using the images and the radar points to determine the position, orientation and velocity of the remote vehicle.
 10. A method for tracking a remote vehicle which is moving in a region of interest in proximity to a host vehicle, said method comprising: providing data from two radar sensors onboard the host vehicle, where the radar sensors have coverage areas which overlap such that at least part of the remote vehicle is sensed by both of the radar sensors when the remote vehicle is in the region of interest, and where the data from the radar sensors includes radar points identifying position and Doppler range rate of points on the remote vehicle; identifying two or more wheels on the remote vehicle from the radar points, including clustering the radar points into groups based on positional proximity, and identifying as a wheel any of the groups which include widely varying Doppler range rate measurements; providing wheel location measurements for the two or more wheels from the two radar sensors, where the wheel location measurements identify a range and an azimuth angle of a center of each of the wheels relative to each of the radar sensors; computing, using a microprocessor, a position, orientation and velocity of the remote vehicle relative to the host vehicle, using a fusion calculation including the wheel location measurements; computing an alignment calibration angle for one of the radar sensors using a fusion calculation including the wheel location measurements; and using the position, orientation and velocity of the remote vehicle in a lateral collision prevention (LCP) system, where the region of interest is located to one side of the host vehicle, and the LCP system issues a warning if the remote vehicle enters a warning zone and applies host vehicle brakes and/or steering if the remote vehicle enters a collision-imminent envelope.
 11. The method of claim 10 wherein clustering the radar points into groups based on positional proximity includes computing a normalized function using a difference in range values and a difference in azimuth angle values for two points, and only including the two points in a group if the normalized function has a value that does not exceed one.
 12. The method of claim 10 wherein identifying as a wheel any of the groups which include widely varying Doppler range rate measurements includes computing expected relative radial velocities of a wheel top point and a wheel bottom point on the remote vehicle with respect to the host vehicle, and identifying as a wheel any of the groups which include Doppler range rate measurements substantially matching the expected relative radial velocities of the wheel top point and the wheel bottom point.
 13. The method of claim 10 wherein computing a position, orientation and velocity of the remote vehicle relative to the host vehicle includes computing the orientation of the remote vehicle based on the wheel location measurements for two wheels on a side of the remote vehicle nearest the host vehicle, and further includes using an algorithm which recursively predicts a state of the remote vehicle which corresponds with the wheel measurement locations, where the state of the remote vehicle includes a two-dimensional position and a two-dimensional velocity.
 14. An object detection system for a host vehicle, said system comprising: two radar sensors onboard the host vehicle, where the radar sensors have coverage areas which overlap such that at least part of the remote vehicle is sensed by both of the radar sensors when the remote vehicle is in the region of interest, and where the data from the radar sensors includes radar points identifying position and Doppler range rate of points on the remote vehicle; and an object detection processor including a microprocessor and a memory module, said processor being programmed to: identify two or more wheels on the remote vehicle from the radar points, including clustering the radar points into groups based on positional proximity, and identifying as a wheel any of the groups which include widely varying Doppler range rate measurements; provide wheel location measurements for the two or more wheels from the two radar sensors, where the wheel location measurements identify a range and an azimuth angle of a center of each of the wheels relative to each of the radar sensors; compute a position, orientation and velocity of the remote vehicle relative to the host vehicle, using a fusion calculation including the wheel location measurements; and compute an alignment calibration angle for one of the radar sensors using a fusion calculation including the wheel location measurements.
 15. The object detection system of claim 14 wherein clustering the radar points into groups based on positional proximity includes computing a normalized function using a difference in range values and a difference in azimuth angle values for two points, and only including the two points in a group if the normalized function has a value that does not exceed one.
 16. The object detection system of claim 14 wherein identifying as a wheel any of the groups which include widely varying Doppler range rate measurements includes computing expected relative radial velocities of a wheel top point and a wheel bottom point on the remote vehicle with respect to the host vehicle, and identifying as a wheel any of the groups which include Doppler range rate measurements substantially matching the expected relative radial velocities of the wheel top point and the wheel bottom point.
 17. The object detection system of claim 14 wherein the processor computes the orientation of the remote vehicle based on the wheel location measurements for two wheels on a side of the remote vehicle nearest the host vehicle.
 18. The object detection system of claim 14 wherein the processor computes the position, orientation and velocity of the remote vehicle relative to the host vehicle using an algorithm which recursively predicts a state of the remote vehicle which corresponds with the wheel measurement locations, where the state of the remote vehicle includes a two-dimensional position and a two-dimensional velocity.
 19. The object detection system of claim 14 wherein the region of interest is located to one side of the host vehicle, the object detection system provides position, orientation and velocity data for the remote vehicle to a lateral collision prevention (LCP) system, and the LCP system issues a warning if the remote vehicle enters a warning zone and applies host vehicle brakes and/or steering if the remote vehicle enters a collision-imminent envelope.
 20. The object detection system of claim 14 further comprising a camera onboard the host vehicle, where the camera provides images which cover a field of view which overlaps the coverage areas of the radar sensors such that the remote vehicle is sensed by the camera and at least one of the radar sensors, and the object detection processor performs a fusion calculation using the images and the radar points to determine the position, orientation and velocity of the remote vehicle. 